[draft] chore(deps): pin django-ansible-base to tag and enable Renovate - #1659
Draft
B-Whitt wants to merge 1 commit into
Draft
[draft] chore(deps): pin django-ansible-base to tag and enable Renovate#1659B-Whitt wants to merge 1 commit into
B-Whitt wants to merge 1 commit into
Conversation
Switch DAB from branch-tracking (branch = "devel") to tag-pinned (tag = "2026.6.2") so Renovate can detect new releases and open version-aware PRs automatically. Enable Renovate's Poetry manager with DAB-specific rules: weekly schedule, loose versioning for CalVer tags, run-e2e label, and manual review (no automerge). Assisted by: Claude Opus 4.6
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
B-Whitt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Currently, eda-server pins django-ansible-base (DAB) to
branch = "devel"inpyproject.toml. Therefore, any timepoetry lockis run during normal eda-server development — for example, dependency update for a CVE fix — it silently picks up whatever changes have landed on DAB'sdevelbranch as a side effect. This couples unrelated changes together: a routine dependency bump can inadvertently pull in new DAB features, breaking changes, or migrations.The goal of this PR is to separate these concerns. DAB updates will run independently on their own schedule, in their own PRs, with clear version visibility.
Summary
tag = "2026.6.2"instead ofbranch = "devel"inpyproject.tomlpoetry.lockto the tagged commitrenovate.jsonwith DAB-specific rules:looseversioning to handle DAB's CalVer formatrun-e2elabel on PRs to trigger end-to-end testsChanges
pyproject.toml—branch = "devel"→tag = "2026.6.2"poetry.lock— re-resolved to DAB2026.6.2(commit07acd71)renovate.json— addedpoetrytoenabledManagers, addedpackageRulesfor DABPrerequisites
ansible/eda-server(likely already is sincerenovate.jsonis active for Tekton updates)Notes
autoupdate-poetry.ymlworkflow is unchanged — it continues handling lockfile drift for other dependenciestag =tobranch = "devel"and removepoetryfromenabledManagersTest Plan
task testpasses (unit tests confirmed, integration needstask docker:up:minimal)npx renovate-config-validator renovate.jsonpassesJira
Resolves: AAP-89364